Real-time vulnerability monitoring

ABSTRACT

An apparatus is provided including at least one platform; an intrusion prevention system configured to communicative couple with the at least one platform; a firewall configured to communicative couple with the at least one platform; at least one first data storage configured to communicative couple with the at least one platform; and at least one second data storage configured to communicative couple with the at least one platform. The at least one platform is configured to perform a plurality of operations that collective protect one or more networked devices.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/138,014 filed Dec. 21, 2013 which, in turn, is a continuation of U.S.patent application Ser. No. 10/882,852, filed Jul. 1, 2004 which, inturn, claims the benefit of U.S. Provisional Application No. 60/484,085,titled SECURITY MANAGEMENT PROXY SYSTEM AND METHODS and filed Jul. 1,2003. This application is also related to issued U.S. Pat. No.8,266,699, titled MULTIPLE-PATH REMEDIATION, as well as applicationstitled POLICYPROTECTION PROXY (U.S. patent application Ser. No.10/882,853), VULNERABILITY AND REMEDIATION DATABASE (U.S. patentapplication Ser. No. 10/882,788), AUTOMATED STAGED PATCH AND POLICYMANAGEMENT (U.S. patent application Ser. No. 10/884,329), and CLIENTCAPTURE OF VULNERABILITY DATA (U.S. patent application Ser. No.10/883,376), all filed on Jul. 1, 2004. All of these applications arehereby incorporated herein by reference as if fully set forth.

FIELD OF THE INVENTION

The present invention relates to computer systems, and more particularlyto management of security of computing and network devices that areconnected to other such devices.

BACKGROUND

With the growing popularity of the Internet and the increasing relianceby individuals and businesses on networked computers, network securitymanagement has become a critical function for many people. Furthermore,with computing systems themselves becoming more complex, securityvulnerabilities in a product are often discovered long after the productis released into general distribution. Improved methods are needed,therefore, for managing updates and patches to software systems, and formanaging configurations of those systems.

The security management problem is still more complex, though. Oftentechniques intended to remediate vulnerabilities (such as configurationchanges, changes to policy settings, or application of patches) addadditional problems. Sometimes patches to an operating system orapplication interfere with operation of other applications, and caninadvertently disable mission-critical services and applications of anenterprise. At other times, remediation steps open other vulnerabilitiesin software. There is, therefore, a need for improved securitymanagement techniques.

SUMMARY

An apparatus is provided including at least one platform; an intrusionprevention system configured to communicative couple with the at leastone platform; a firewall configured to communicative couple with the atleast one platform; at least one first data storage configured tocommunicative couple with the at least one platform; and at least onesecond data storage configured to communicative couple with the at leastone platform. The at least one platform is configured to receive aresult of at least one operation in connection with at least one of aplurality of networked devices, the at least one operation based onfirst information from the at least one first data storage identifying aplurality of potential vulnerabilities including at least one firstpotential vulnerability and at least one second potential vulnerability.The at least one operation is configured for: identifying at least oneconfiguration associated with the at least one networked device, anddetermining that the at least one networked device is actuallyvulnerable to at least one actual vulnerability, based on the identifiedat least one configuration and the first information from the at leastone first data storage identifying the plurality of potentialvulnerabilities, such that second information associated with the resultis stored in the at least one second data storage separate from the atleast one first data storage, the second information relating to the atleast one actual vulnerability to which the at least one networkeddevice is actually vulnerable. The at least one platform is furtherconfigured to cause display, via at least one user interface, aplurality of techniques including a first technique for utilizing theintrusion prevention system for occurrence mitigation, a secondtechnique for utilizing the firewall for occurrence mitigation. Further,the at least one platform is further configured to allow receipt of:user input causing selection of the first technique for utilizing theintrusion prevention system for occurrence mitigation, and user inputcausing selection of the second technique for utilizing the firewall foroccurrence mitigation. Still yet, the at least one platform is furtherconfigured to, based on the user input causing selection of the firsttechnique for utilizing the intrusion prevention system for occurrencemitigation, automatically apply the first technique for utilizing theintrusion prevention system for occurrence mitigation; and based on theuser input causing selection of the second technique for utilizing thefirewall for occurrence mitigation, automatically apply the secondtechnique for utilizing the firewall for occurrence mitigation. Evenstill, the at least one platform is further configured to causeidentification of: in connection with the at least one networked device,a first occurrence including at least one first occurrence packetdirected to the at least one networked device, and in connection withthe at least one networked device, a second occurrence including atleast one second occurrence packet directed to the at least onenetworked device. Even still yet, the at least one platform is furtherconfigured to determine: that the first occurrence including the atleast one first occurrence packet directed to the at least one networkeddevice is capable of taking advantage of the at least one of the actualvulnerability to which the at least one networked device is actuallyvulnerable; and that the second occurrence including the at least onesecond occurrence packet directed to the at least one networked deviceis not capable of taking advantage of the at least one of the actualvulnerability to which the at least one networked device is actuallyvulnerable. Further, the at least one platform is configured to cause areporting of at least the first occurrence based on the determinationthat the first occurrence including the at least one first occurrencepacket directed to the at least one networked device is capable oftaking advantage of the at least one of the actual vulnerability towhich the at least one networked device is actually vulnerable.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a networked system of computers in oneembodiment of the present invention.

FIG. 2 is a block diagram showing components of several computingdevices in the system of FIG. 1.

FIGS. 3 and 4 trace signals that travel through the system of FIGS. 1and 2 and the present invention is applied to them.

FIG. 5A is a flow chart of a filtering proxy method according to oneembodiment of the present invention.

FIGS. 5B and 6 illustrate a platform, in accordance with possibleembodiments.

FIG. 7 illustrates an intelligent IDS, in accordance with oneembodiment.

FIG. 8 illustrates an update system, in accordance with one embodiment.

FIG. 9 shows a configured network, in accordance with one embodiment.

FIG. 10 shows policy compliance and enforcement, in accordance with oneembodiment.

FIG. 11 illustrates an intelligent IPS, in accordance with oneembodiment.

FIG. 12 illustrates an SDK function call flow, in accordance with oneembodiment.

DESCRIPTION

For the purpose of promoting an understanding of the principles of thepresent invention, reference will now be made to the embodimentillustrated in the drawings and specific language will be used todescribe the same. It will, nevertheless, be understood that nolimitation of the scope of the invention is thereby intended; anyalterations and further modifications of the described or illustratedembodiments, and any further applications of the principles of theinvention as illustrated therein are contemplated as would normallyoccur to one skilled in the art to which the invention relates.

Generally, the present invention in one embodiment operates in thecontext of a network as shown in FIG. 1. System 100 includes avulnerability and remediation database 110 connected by Internet 120 tosubnet 130. In this exemplary embodiment, firewall 131 serves as thegateway between Internet 120 and the rest of subnet 130. Router 133directs connections between computers 137 and each other and otherdevices on Internet 120. Server 135 collects certain information andprovides certain data services that will be discussed in further detailherein.

In particular, security server 135 includes processor 142, and memory144 encoded with programming instructions executable by processor 142 toperform several important security-related functions. For example,security server 135 collects data from devices 131, 133, 137, and 139,including the software installed on those devices, their configurationand policy settings, and patches that have been installed. Securityserver 135 also obtains from vulnerability and remediation database 110a regularly updated list of security vulnerabilities in software for awide variety of operating systems, and even in the operating systemsthemselves. Security server 135 also downloads a regularly updated listof remediation techniques that can be applied to protect a device fromdamage due to those vulnerabilities. In one embodiment, eachvulnerability in remediation database 110 is identified by avulnerability identifier, and the vulnerability identifier can be usedto retrieve remediation information from database 110 (and from database146, discussed below in relation to FIG. 2).

In one embodiment, computers 137 and 139 each comprise a processor 152,162, memory 154, 164, and storage 156, 166. Computer 137 executes aclient-side program (stored in storage 156, loaded into memory 154, andexecuted by processor 152) that maintains an up-to-date collection ofinformation regarding the operating system, service pack (ifapplicable), software, and patches installed on computer 137, and thepolicies and configuration data (including configuration files, andelements that may be contained in files, such as *.ini and *.conf filesand registry information, for example), and communicates thatinformation on a substantially real-time basis to security server 135.In an alternative embodiment, the collection of information is notretained on computer 137, but is only communicated once to securityserver 135, then is updated in real time as changes to that collectionoccur.

Computer 139 stores, loads, and executes a similar software program thatcommunicates configuration information pertaining to computer 139 tosecurity server 135, also substantially in real time. Changes to theconfiguration registry in computer 139 are monitored, and selectedchanges are communicated to security server 135 so that relevantinformation is always available. Security server 135 may connectdirectly to and request software installation status and configurationinformation from firewall 131 and router 133, for embodiments whereinfirewall 131 and router 133 do not have a software program executing onthem to communicate this information directly.

This collection of information is made available at security server 135,and combined with the vulnerability and remediation data from source110. The advanced functionality of system 100 is thereby enabled asdiscussed further herein.

Turning to FIG. 2, one sees additional details and components of thedevices in subnet 130. Computers 137 and 139 are traditional client orserver machines, each having a processor 152, 162, memory 154, 164, andstorage 156, 166. Firewall 131 and router 133 also have processors 172,182 and storage 174, 184, respectively, as is known in the art. In thisembodiment, devices 137 and 139 each execute a client-side program thatcontinuously monitors the software installation and configuration statusfor that device. Changes to that status are communicated insubstantially real time to security server 135, which continuouslymaintains the information in database 146. Security server 135 connectsdirectly to firewall 131 and router 133 to obtain software installationand configuration status for those devices in the absence of aclient-side program running thereon.

Processors 142, 152, 162 may each be comprised of one or more componentsconfigured as a single unit. Alternatively, when of a multi-componentform, processor 142, 152, 162 may each have one or more componentslocated remotely relative to the others. One or more components ofprocessor 142, 152, 162 may be of the electronic variety definingdigital circuitry, analog circuitry, or both. In one embodiment,processor 142, 152, 162 are of a conventional, integrated circuitmicroprocessor arrangement, such as one or more PENTIUM 4 or XEONprocessors from INTEL Corporation of 2200 Mission College Boulevard,Santa Clara, Calif., 95052, USA, or ATHLON XP processors from AdvancedMicro Devices, One AMD Place, Sunnyvale, Calif., 94088, USA.

Memories 144, 154, 164 may include one or more types of solid-stateelectronic memory, magnetic memory, or optical memory, just to name afew. By way of non-limiting example, memory 40 b may include solid-stateelectronic Random Access Memory (RAM), Sequentially Accessible Memory(SAM) (such as the First-In, First-Out (FIFO) variety or the Last-InFirst-Out (LIFO) variety), Programmable Read Only Memory (PROM),Electrically Programmable Read Only Memory (EPROM), or ElectricallyErasable Programmable Read Only Memory (EEPROM); an optical disc memory(such as a DVD or CD ROM); a magnetically encoded hard drive, floppydisk, tape, or cartridge media; or a combination of any of these memorytypes. Also, memories 144, 154, 164 may be volatile, nonvolatile, or ahybrid combination of volatile and nonvolatile varieties.

In this exemplary embodiment, storage 146, 156, 166 comprises one ormore of the memory types just given for memories 144, 154, 164,preferably selected from the non-volatile types.

This collection of information is used by system 100 in a wide varietyof ways. With reference to FIG. 3, assume for example that a connectionrequest 211 arrives at firewall 131 requesting that data be transferredto computer 137. The payload of request 211 is, in this example, a proberequest for a worm that takes advantage of a particular securityvulnerability in a certain computer operating system. Based oncharacteristics of the connection request 211, firewall 131 sends aquery 213 to security server 135. Query 213 includes information thatsecurity server 135 uses to determine (1) the intended destination ofconnection request 211, and (2) some characterization of the payload ofconnection request 211, such as a vulnerability identifier. Securityserver 135 uses this information to determine whether connection request211 is attempting to take advantage of a particular known vulnerabilityof destination machine 137, and uses information from database 146 (seeFIG. 2) to determine whether the destination computer 137 has thevulnerable software installed, and whether the vulnerability has beenpatched on computer 137, or whether computer 137 has been configured soas to be invulnerable to a particular attack.

Security server 135 sends result signal 217 back to firewall 131 with anindication of whether the connection request should be granted orrejected. If it is to be granted, firewall 131 passes the request torouter 133 as request 219, and router 133 relays the request as request221 to computer 137, as is understood in the art. If, on the other hand,signal 217 indicates that connection request 211 is to be rejected,firewall 133 drops or rejects the connection request 211 as isunderstood in the art.

Analogous operation can protect computers within subnet 130 fromcompromised devices within subnet 130 as well. For example, FIG. 4illustrates subnet 130 with computer 137 compromised. Under the controlof a virus or worm, for example, computer 137 sends connection attempt231 to router 133 in an attempt to probe or take advantage of apotential vulnerability in computer 139. On receiving connection request231, router 133 sends relevant information about request 231 in a query233 to security server 135. Similarly to the operation discussed abovein relation to FIG. 3, security server 135 determines whether connectionrequest 231 poses any threat, and in particular any threat to softwareon computer 139. If so, security server 135 determines whether thevulnerability has been patched, and if not, it determines whethercomputer 139 has been otherwise configured to avoid damage due to thatvulnerability. Security server 135 replies with signal 235 to query 233with that answer. Router 133 uses response 235 to determine whether toallow the connection attempt.

In some embodiments, upon a determination by security server 135 that aconnection attempt or other attack has occurred against a computer thatis vulnerable (based on its current software, patch, policy, andconfiguration status), security server 135 selects one or moreremediation techniques from database 146 that remediate the particularvulnerability. Based on a prioritization previously selected by anadministrator or the system designer, the remediation technique(s) areapplied (1) to the machine that was attacked, (2) to all devices subjectto the same vulnerability (based on their real-time software, patch,policy, and configuration status), or (3) to all devices to which theselected remediation can be applied.

In various embodiments, remediation techniques include the closing ofopen ports on the device; installation of a patch that is known tocorrect the vulnerability; changing the device's configuration;stopping, disabling, or removing services; setting or modifyingpolicies; and the like. Furthermore, in various embodiments, events andactions are logged (preferably in a non-volatile medium) for lateranalysis and review by system administrators. In these embodiments, thelog also stores information describing whether the target device wasvulnerable to the attack.

A real-time status database according to the present invention has manyother applications as well. In some embodiments, the database 146 ismade available to an administrative console running on security server135 or other administrative terminal. When a vulnerability is newlydiscovered in software that exists in subnet 130, administrators canimmediately see whether any devices in subnet 130 are vulnerable to it,and if so, which ones. If a means of remediation of the vulnerability isknown, the remediation can be selectively applied to only those devicessubject to the vulnerability.

In some embodiments, the database 146 is integrated into another device,such as firewall 131 or router 133, or an individual device on thenetwork. While some of these embodiments might avoid some failures dueto network instability, they substantially increase the complexity ofthe device itself. For this reason, as well as the complexity ofmaintaining security database functions when integrated with otherfunctions, the network-attached device embodiment described above inrelation to FIGS. 1-4 is one possible embodiment.

In one embodiment, a software development kit (SDK) allows programmersto develop security applications that access the data collected indatabase 146. The applications developed with the SDK access informationusing a defined application programming interface (API) to retrievevulnerability, remediation, and device status information available tothe system. The applications then make security-related determinationsand are enabled to take certain actions based on the available data.

In these exemplary systems, “configuration information” for each devicemay take the form of initialization files (often named *.ini or *.conf),configuration registry (such as, the Windows Registry on MicrosoftWINDOWS operating systems), or configuration data held in volatile ornon-volatile memory. Such configuration information often determineswhat and how data is accepted from other devices, sent to other devices,processed, stored, or otherwise handled, and in many cases determineswhat routines and sub-routines are executed in a particular applicationor operating system.

In one embodiment, security information management system is provided,wherein a database of potential vulnerabilities is maintained, alongwith data describing remediation techniques (patches, policy settings,and configuration options) available to protect against them. At leastone vulnerability is associated in the database with multiple availableremediation techniques. In one embodiment, the system presents a userwith the list of remediation techniques available to protect against aknown vulnerability, accepts the user's selection from the list, andexecutes the selected technique. In other embodiments, the system uses apredetermined prioritization schedule to automatically select among theavailable remediation techniques, then automatically executes theselected technique.

One embodiment of the present invention is a database of informationabout a plurality of devices, updated in real-time and used by anapplication to make a security-related decision. The database storesdata indicating the installed operating system(s), installed software,patches that have been applied, system policies that are in place, andconfiguration information for each device. The database answers queriesby one or more devices or applications attached by a network tofacilitate security-related decision making. In one form of thisembodiment, a firewall or router handles a connection request ormaintenance of a connection based on the configuration informationstored in the database that relates to one or both of the devicesinvolved in the transmission.

In one embodiment, database 146 includes vulnerability and remediationinformation such that, for at least one vulnerability, multiple methodsof remediating the vulnerability are specified. When the system hasoccasion to implement or offer remediation of a vulnerability, all knownalternatives are presented that are relevant to the device or machine'sparticular configuration or setup. For example, when a vulnerability ofa device is presented to an administrator, the administrator is given achoice among the plurality of remediation options to remediate thevulnerability. In some embodiments, the administrator can select apreferred type of remediation that will be applied if available and afallback type. For example, an administrator may select application of apolicy setting over installation of a software patch, so that the riskof disruption of critical business systems is minimized.

In other embodiments, an administrator or other user is presented with aset of user interface elements that identify multiple options forremediating and identifying the vulnerability. The administrator or userselects the method to be used, and that remediation is applied to thevulnerable device(s).

FIG. 5A is a flow chart of a filtering proxy method according to oneembodiment of the present invention.

In use, a database maintains security status information on each devicein a network, based on whether the device's operating system, software,and patches are installed and configured to meet a baseline level ofsecurity. A network gateway proxy blocks connection attempts fromdevices for which the database indicates a substandard security status,but allows connections from other devices to pass normally. The databaseis preferably updated on a substantially real-time basis by client-sidesoftware run by each device in the network.

Another form of the present embodiment includes a connection proxy thatfilters connections originating within the network. In particular, oneembodiment employs a proxy that denies connection attempts originatingwith devices in the network when the originating device has a status,reflected in the database, that fails to meet predetermined securitycharacteristics in terms of installed operating system and software,patch levels, and system policy and configuration registry information.

In this embodiment, router 133 serves as a connection proxy for devicesand subnet 130, as will be understood by those skilled in the art. Inaddition to basic proxy functionality, however, router 133 accessesdatabase 146 on security server 135 via the SDK at each connectionattempt. If, for example, device 137 attempts to connect to any devicewhere the connection must pass through the proxy server (router 133 inthis example), such as a device on Internet 120, router 133 checks thesecurity status of device 137 in database 146, using the real-timestatus therein to determine whether device 137 complies with one or morepredetermined security policies. If it does, router 133 allows theconnection to be made. If it does not, router 133 prevents theconnection, preferably redirecting the connection to a diagnostic pagethat explains why the connection is not being made.

This system is illustrated by method 200 in FIG. 5A. Method 200 beginswith start point 201. The proxy (router 133 in the above example)receives a connection request at block 203, then retrieves the securitystatus of the source device at block 205. This preferably uses thereal-time updated status information from database 146 (see FIG. 2) atdecision block 207. If the security status indicates that the sourcedevice complies with the predetermined security policy, the proxy allowsthe connection at block 209. If not, the proxy refuses the connection atblock 211 and redirects the connection to an explanation message (suchas a locally generated web page or other message source) at block 213.In either case, method 200 ends at end point 219.

In possible embodiments, the determination and decision at block 207apply a comprehensive minimum policy set that protects other devices insubnet 130 (see FIG. 1) from viruses, trojans, worms, and other malwarethat might be inadvertently and/or carelessly acquired due to therequested connection.

In another embodiment, a security information management system isprovided, wherein client-side devices preferably collect and monitorinformation describing the operating system, software, and patchesinstalled on the device(s), as well as configuration thereof. A databaseof this information is maintained, along with data describingvulnerabilities of available software and associated remediationtechniques available for it. The system exposes an API to supportsecurity-related decisions by other applications. For example, anintrusion detection system (IDS) accesses the database to determinewhether an actual threat exists and should be (or has been) blocked.

In another form of this embodiment, client software runs on eachmonitored device and reports configuration information to the database,so that the database has substantially real-time-current information.

The present embodiment of the present invention advantageously acquiresthe real-time status information from each client using client-sidesoftware. In this manner, a resource burden of monitoring is spreadamong the devices being monitored, and uses far fewer network resourcesin the process.

In these exemplary systems, “configuration information” for each devicemay take the form of initialization files (often named *.ini or *.conf),configuration registry (such as the Windows Registry on MicrosoftWindows operating systems), or configuration data held in volatile ornon-volatile memory. Such configuration information often determineswhat and how data is accepted from other devices, sent to other devices,processed, stored, or otherwise handled, and in many cases determineswhat routines and sub-routines are executed in a particular applicationor operating system.

In one embodiment, a system maintains a database of vulnerabilities andassociated remediation techniques. The remediation techniques includesoftware patches, policy settings or changes, and registry settings orchanges. This multi-faceted provides novel flexibility in management ofsecurity issues, and convenience for security administrators in bothdetermining available options and selecting remediation steps forvulnerable systems.

In another embodiment of the present invention, patches, policy changes,software updates, and configuration changes are rolled out to devices ona network using a staged roll-out technique. In this technique, thechange is applied to a selected device or set of devices identified byan administrator. After a predetermined amount of time passes, unlessthe administrator has canceled the roll-out, the change is applied to anadditional group of devices on the network. Third- and fourth-tiergroups may also be identified by the administrator, where implementationof the remediation or upgrade is automatically effected in subsequentstages a predetermined amount of time after the preceding stageroll-out. Thus, if no failures are noted following a more limitedroll-out (on a first set of devices), then the remediation or upgrade isautomatically applied to other devices. If, on the other hand, an erroror failure is observed, the subsequent roll-out can be canceled so thatfurther failures and problems are avoided.

FIGS. 5B and 6 illustrate a platform, in accordance with possibleembodiments.

In one possible embodiment, provided is a platform and underlying backend that includes a logic engine and vulnerability data warehouse. Itmay easily integrate with and enable network security products such asIDS, scanners, or firewalls to intelligently reference and share thesame vulnerability data set, and independently provide completevulnerability remediation (patching) functionalities such as thatprovided by the patch management and vulnerability remediationapplication. Thereby, the technology may improve system accuracy andefficiencies, minimize false positives and false negatives, and providepolicy compliance and enforcement capabilities.

The latest network compromises are combining qualities of viruses,worms, and denial of service attacks into new blended attacks.Additionally, blended attacks may now utilize metamorphic or polymorphicabilities to change their signatures to avoid detection. To mitigatethese new risks, organizations are now deploying a multi-tiered networkdefense strategy comprised of a variety of network security componentslayered at the perimeter and to internal network machines and devices.The security components are managed separately, and possibly their datais ported into a Security Information Management System (SIMS)correlation engine.

However, network security components and correlation engines rely onsignatures or anomalies, producing an ever-increasing quantity of data,including false positive, benign, and erroneous events. They also lackthe intelligence to identify, reference, or remediate thevulnerabilities targeted by the attack. Furthermore, the time and costto acquire, manage, and maintain these numerous network securitycomponents is overwhelming the end user. Therefore, more sophisticatedtechnology is provided to resolve these performance and managementissues.

In one embodiment, technology may be provided that addresses theserequirements by making each security component smarter and providesmanagers with remote remediation options. Thereby, improving systemperformance and streamlining management processes.

In one embodiment, an intelligent integration platform and SDK areprovided to meet the above requirements.

In one embodiment, security products are enhanced and systemintelligence may be provided. The same vulnerability data warehouseinformation is shared with the products so that more intelligent actionsmay then be taken to mitigate complex threats.

One embodiment cross-references the threat's identifier with thetarget's configuration. The threat's CVE ID, or other identifier, andthe destination IP address are fed into the logic engine where itcross-references the threat with the machine's existing OS, application,and patch configuration profile. An answer is returned accuratelyindicating if the machine is vulnerable.

In one embodiment, network vulnerabilities are identified. The platformmay independently identify which network machines and devices havevulnerabilities by querying a client agent, or a device's OS or firmwaredirectly.

One embodiment proactively remediates the vulnerability. Once avulnerability is identified, a remediation function may be provided thatmay remotely and automatically deploy the appropriate update to eachmachine or device, install it, and document it with change tracking andaudit trail reports.

Examples of Anti-Vulnerability applications that may be integrated intonetwork security products for enterprise and small office home office(SOHO) networks when integrated with one embodiment, via the SDK, willbe described.

In one embodiment, update or patch deployment are provided, whichremotely remediate network vulnerabilities and provide policy complianceand enforcement capabilities. And, for the consumer market, it mayadditionally support non-security related updates such as applicationversion, performance, and bug-fix upgrades.

In one embodiment, an IDS may be provided that accurately determines ifthe targeted machine is actually vulnerable to an attack; virtuallyeliminates false positives and false negatives; and adds vulnerabilityremediation and policy compliance and enforcement functionalities.

In one embodiment, a scanner may be provided that virtually eliminatesfalse positive and false negatives, and adds vulnerability remediationand policy compliance and enforcement functionalities.

In one embodiment, a firewall may be provided that virtually eliminatesfalse positive and false negatives, preventing the security system fromdenying valid traffic to the organization—self-inflicted denial ofservice attacks—and adds vulnerability remediation, and policycompliance and enforcement functionalities.

In one embodiment, vulnerability management may be provided, as setforth above.

In one embodiment, multiple products are provided including an IDS,scanner, and firewall. Each may communicate with the same back-end datawarehouse, sharing the same vulnerability information, attainingintelligence and more accurate information about the target and itsvulnerabilities, thereby more effectively mitigating complex threats.

In one embodiment, change management may be provided, which mayautomatically create a change request in the system, specifying whatupdate/patch is applicable to what system or groups of systems byvulnerability. After approval of the request, they may automaticallydeploy and install the update/patch. Finally, they may also verifycorrect operation after installation and automatically provide allnecessary documentation and logging required.

Lastly, the platform may also provide product upgrades and signatureupdates to each of these various security products.

The platform is comprised of the following software components: SDK,client agent, logic engine, and data warehouse stored on a dedicatedon-site server. Network operations center (NOC) Servers periodicallysynchronize the customers' servers with the latest vulnerability andupdate data. See FIG. 5B.

The same client agent and on-site server support all securityapplications that are integrated onto the platform, thereby providingthe added anti-vulnerability functionalities presented in the previoussection.

There are two system requirements: TCP/IP connectivity, and supportednetwork machines and devices. In one embodiment, platforms supported areset forth below in Table 1.

TABLE 1   All Windows Operating Systems and their applications All UNIXvariants Cisco routers and firewalls Toshiba network devices Netgearnetwork devices Linksys network devices, including wireless accesspoints

Platform support is scalable to any network size or architecture;consumer, small office home office (SOHO), enterprise, and distributednetworks.

In one embodiment, technology may be provided that includes a backendplatform that includes a logic engine and vulnerability data warehouse.It may easily integrate with and enable network security products suchas IDS, scanners, or firewalls to intelligently reference and share thesame vulnerability data set, and independently provide completevulnerability remediation (patching) functionalities such as thatprovided by the patch management and vulnerability remediationapplication, update application and the intelligent IDS. Thereby, thetechnology may improve system accuracy and efficiencies, minimize falsepositives and false negatives, and provide policy compliance andenforcement capabilities.

As shown in FIG. 5B, the technology may meet market requirements,presented in the next section.

For example, networks are probed at an ever-increasing frequency forvulnerabilities, which may be exploited with compromise attacks. Toprotect the network, administrators have traditionally set up perimeterdefense strategies.

These strategies generally call for network managers to lock down coreservers, and monitor/scan/filter all incoming and outgoing traffic atthe network perimeter with several network security products such asantivirus and firewalls to identify and attempt to neutralize hackersand malicious code. In the past, these strategies worked well, howevernew threats are becoming more complex.

The latest malicious code may combine qualities of viruses, worms, anddirect compromise attacks into new blended attacks. Virus payloads arebecoming more complex and by using metamorphic or polymorphic abilities,viruses are able to change their signatures to avoid thefingerprint-type filtering that most applications employ.

To mitigate these new risks, organizations deploy a multi-tiered networkdefense strategy comprised of a variety of additional network securityproducts layered at the perimeter and to internal network machines anddevices. Such network security products include antivirus, firewall,scanners, and network and host based intrusion detection systems.

Each of these systems is based on specific signatures, rules, oranomalies of each attack and their variants, and do not identify andremediate the specific network vulnerabilities the attack is targeting.So each attack, and its variants, must be identified and analyzed, asignature prepared, then finally deployed to each point product on eachcustomer's network. This process is uncoordinated among multipledisparate systems, and creates an ever-increasing number of signaturesproducing more and more attack alerts requiring immediate attention—manyof which are erroneous. The security components are managed separately,and possibly their data is ported into a security information managementsystem (SIMS) correlation engine.

Additionally, to proactively remediate the vulnerabilities the maliciouscode is targeting, administrators quickly and diligently update or“patch” each network machine and device, which is a time-consuming andcostly process. Further compounding the burden on administrators, bestpractice and government compliance directives may require higherstandards of network security and integrity to protect consumer privacy,and they are documented with change tracking and audit trail reports.

Therefore, it is increasingly difficult and costly to effectivelymitigate new threats and manage numerous systems—particularly in anenvironment of rising security standards and policy compliancerequirements.

Thus, the multi-tiered network defense strategy is falling shortprimarily for four reasons. First, there is an inability of multi-tierednetwork security products to communicate and share information necessaryto mitigate blended threats, and minimize false positives and falsenegatives. The vulnerabilities targeted by malicious code are notaccurately identified nor proactively remediated. The associatedexcessive aggregate cost of ownership of multiple systems. The excessiveadministrative burden and cost of managing and maintaining multiplesystems.

Hence, there is a need to integrate systems, share informationintelligently to better defend against blended threats, reducemanagement and cost requirements, and automate vulnerabilityidentification and remediation functionalities, as presented in thehigh-level requirements.

In one embodiment, technology is provided to meet the following marketrequirements: integrate network security products to share information;provide system intelligence; and remediate network vulnerabilities.

In one embodiment, technology may integrate with and enable networksecurity products to intelligently reference and share information fromthe same vulnerability data set, provide vulnerability identificationand remediation functionalities, and efficiently meet policy complianceand enforcement requirements.

In one embodiment, the platform is a complimentary network securitytechnology. When integrated into the defense strategy, it addsintelligence that more accurately and efficiently mitigates blendedthreats and offloads the time-consuming functions that burden networkadministrators.

In one embodiment, the platform enables network security products toshare information via its proprietary logic engine to automaticallycross-reference the threat identifier with the targeted machine'sconfiguration to determine if it is actually vulnerable to that threat.Previously separate and uncoordinated processes are now more intelligentand automated, resulting in improved system accuracy and efficiency.Therefore the need to layer more and more point products and add a SIMSis reduced, in-turn decreasing the amount of data—particularly erroneousdata—to manage. Subsequently, the costs to acquire, operate, and managethe additional multiple point products, and the need to implement aSIMS, are also reduced.

In one embodiment, the platform may also remotely and proactivelyremediate vulnerabilities by first determining which updates are neededand compatible with each machine or device, taking into account the OS,applications, or firmware installed. Then, the updates may be deployed,installed, and validated. Thereby, policy compliance is effectively andefficiently enforced, and documented.

In one embodiment, the present technology fulfills market requirementsnoted in the previous section. For example, it may integrate networksecurity products and provides system intelligence. The samevulnerability data warehouse information is shared with all products sothat more intelligent actions may then be taken to mitigate complexthreats.

Still yet, it may cross-reference the threat's identifier with thetarget's configuration. The threat's CVE ID, or other identifier, andthe destination IP address are fed into the logic engine where itcross-references the threat with the machine's existing OS, application,and patch configuration profile. An answer is returned accuratelyindicating if the machine is vulnerable. Thereby, minimizes erroneous,benign, and false positive data produced by each security product.

One embodiment identifies network vulnerabilities. The platform mayindependently identify which network machines and devices havevulnerabilities by querying a client agent, or a device's OS or firmwaredirectly.

One embodiment proactively remediates the vulnerability. Once avulnerability is identified, a remediation function may be provided thatmay remotely and automatically deploy the appropriate update to eachmachine or device, install it, and document it with change tracking andaudit trail reports.

Various possible benefits include blended attacks being more effectivelymitigated and the overwhelming management and maintenance burden onadministrators to purchase, operate, and maintain multiple networksecurity products being reduced, while increasing productivity, reducingcosts, and more effectively and efficiently meeting policy complianceand enforcement requirements.

Table 2 illustrates a plurality of end user details.

TABLE 2 Supplements existing technology to better defend against blendedattacks Intelligently accesses the vulnerability data warehouse, andremediates vulnerabilities. Offers policy compliance and enforcementfunctionality Vulnerabilities may be automatically remediated, verifiedand documented, therefore enforcing compliance. No additional softwareor hardware implementation costs Anti-Vulnerability functionalities maybe integrated into existing product platforms. Reduces cost of ownershipof multi network security products Shared vulnerability data sets andadded vulnerability remediation functionalities may reduce the number ofnetwork security products needed to adequately attain defense strategyrequirements. Reduces management and maintenance costs Increasedaccuracy of vulnerability identification, remediation and policyenforcement, and reduction of false positives, false negatives anddenial of service (DoS), significantly reduces management time andcosts. Manage more machines and devices on the network through oneportal Vulnerability remediation and policy compliance and enforcementmay be integrated with existing security network security products, andtheir respective interfaces. Minimize end user education/ absorptioncosts Anti-Vulnerability applications are transparently integrated,retaining pre- existing architecture, processes, and interfaces.Therefore, the end user experience remains the same, or improved withsimplified or automated processes. User experience remains thesame—additional time or costs to understand and execute new technologiesare minimized Anti-Vulnerability applications may be integratedtransparently and seamlessly, and the pre-existing operational processesand user interfaces are virtually unchanged. Supports both theenterprise and SOHO networks Data warehouse contains vulnerabilities andupdates for many machines and devices that operate on both enterpriseand SOHO networks. Applications presented hereinafter

Examples of applications that may be made available for enterprise andsmall office home office (SOHO) networks when integrated withAnti-Vulnerability technology via the SDK will now be set forth.

In one embodiment, update or patch deployment is provided. In oneembodiment, a patch management and vulnerability remediation solution isprovided. The technology enables products to add accurate vulnerabilityidentification, remediation, verification, and policy compliancefunctions. With such technology, products may gain intelligence,accuracy and efficiency, eliminate false positives and false negatives,and ensure policy compliance, thereby saving the organization time andmoney. Such functionalities and benefits are available for both theenterprise and SOHO networks. And, for the consumer market, it mayadditionally support non-security related updates such as applicationversion, performance, and bug-fix updates for widely distributedprograms, which may optimize system performance and enhance the consumerexperience.

In one embodiment, an IDS is provided. IDS products attempt to identifymalicious code by signatures at both the network and host client level.While they may be able to identify malicious code by CVE ID or otheridentifier, and targeted machines by IP address, but they generally donot have the intelligence to determine if the any of the machines on thenetwork are susceptible to that attack, or with finer granularity, ifany machine has a specific vulnerability to that specific attack, or ifthe targeted vulnerability has already been patched. For example, if themalicious code has been written as a Windows based attack targeting aWindows vulnerability, is the Destination IP actually running Windows,or a UNIX variant? And, if Windows, is it vulnerable to the attack, orhas it already been patched? IDS do not have the intelligence to answerthese questions, and incident alerts are generated indiscriminately.Lastly, even if the targeted machine is vulnerable—it remainsunremediated—an IDS does not have the capability to remediate it.

With the present embodiment, a product architect can integratefunctionalities listed in the previous section to enable the IDS toaccess the Anti-Vulnerability logic engine and platform. It may thenhave the intelligence to determine if any machine on the network issusceptible to the attack, remediate the vulnerability, mitigate theattack, and verify policy compliance. Now, if no machines weresusceptible to the attack, it is identified as an event but not anincident, no further data or alert is generated, and a managementresponse is not required. Integrated products may gain intelligence,accuracy, and efficiency, eliminate false positives and false negatives,and ensure policy compliance, thereby saving the organization time andmoney. Such functionalities and benefits are available for both theenterprise and SOHO networks.

In one embodiment, scanners may be provided. Vulnerability scannersassess each machine on the network for vulnerabilities, and create listsof potential vulnerabilities to the system managers. The lists commonlycontain many false positives and false negatives, burdening the systemand managers with inaccuracies.

With the present embodiment, a product architect can integratefunctionalities listed in the previous section to enable the scanner toaccess the logic engine and platform, and then have the intelligence todetermine if the machine has actual vulnerabilities, remediate them, andverify policy compliance. Integrated products may gain intelligence,accuracy, and efficiency, eliminated false positives and falsenegatives, and ensured policy compliance, thereby saving theorganization time and money.

In one embodiment, a firewall may be provided. “Smart” firewalls arebased in part on signatures and other similar functionalities as the IDSproducts described above.

With the present embodiment, the firewall can determine whether anattack is valid or a false positive, thereby preventing the securitysystem from denying valid traffic to the organization—self-inflicted DoSattacks. Such functionalities and benefits may be available for both theenterprise and SOHO networks.

In one embodiment, vulnerability management may be provided.Vulnerability management products enable managers to set policy andidentify potential network vulnerabilities. They typically do notaccurately identify each vulnerability on each network machine anddevice, nor remediate each vulnerability, meeting policy complianceenforcement requirements.

The present embodiment offers similar functionalities and benefits asthe patch deployment products described above. In short, it enablesproducts to add accurate vulnerability identification, remediation,verification, and policy compliance and enforcement. Suchfunctionalities and benefits are available for both the enterprise andSOHO networks.

To this end, multiple products may be provided: IDS, scanner, firewall,and vulnerability management. Each product functions as the individualproducts noted above. Each may be deployed and operated on the networkin a multi-tiered network defense strategy. They may be disparatesystem, and their signatures and update deployment schedules may vary.Therefore, the probability of mitigating a new and complex threatdecreases, while management requirements and cost increases.

In one embodiment, they each may communicate with the same backend datawarehouse, sharing the same vulnerability information, attainingintelligence and more accurate information about the target and itsvulnerabilities, thereby more effectively mitigating complex threats. Itmay also enable the products to add accurate vulnerabilityidentification, remediation, verification, and policy compliance andenforcement functionalities.

In one embodiment, change management (CM) may be provided. Existing CMapplications control the documentation and logging of change throughoutthe enterprise. These applications ensure that an organization maintainsconsistent records of what happened and when. Currently administratorsmust independently recognize that a security patch/update must bedeployed to a computer or group of computers.

The user enters the request in the system, through the pipelined processof change management the request would be approved, the patch/updatewould be manually installed by a user, then documented in the changemanagement software that the process has been completed. While CMsoftware assists in documentation, very little if any assistance may beprovided to identify the patches/updates needed, nor verifying correctfunction after the update/patch is installed.

With the current possible embodiment, change management integration maygreatly streamline this process further reducing total cost ofownership, ease of use, and a higher standard of documentation. Theproducts may then automatically create a change request in the system,specifying what update/patch is applicable to what system or groups ofsystems by vulnerability. After approval of the request, they mayautomatically deploy and install the update/patch. Finally, they mayalso verify correct operation after installation and automaticallyprovide all necessary documentation and logging required.

Lastly, one possible embodiment may also provide product upgrades andsignature updates to each of these various security products—includingall of the technology benefits such as ensuring compliance of signatureversions, logging, reporting, and verification of installation.

Thus, one possible embodiment includes an intelligent platform that maysupplement any existing defense strategy. Once integrated with thetechnology, security products may share the same vulnerability data setto improve automation and accuracy—increasing efficiencies andminimizing false positives and false negatives. It also enables remoteidentification, management, and remediation of network vulnerabilities,and provides update deployment, validation, and reporting capabilities.Thereby, the technology improves network security and integrity,mitigation of blended threats, while increasing productivity, reducingtotal cost ownership, and more effectively and efficiently attainingpolicy compliance and enforcement requirements.

One embodiment provides IDS intelligence, accuracy and remote patchingfunctions—IDS data output integrated with the aforementioned platformvia the SDK. The platform's underlying backend including a logic engineand vulnerability data warehouse provides the added functions andperformance.

Conventional IDS produce an ever-increasing quantity of alert data,including erroneous and false positive data. They also lack theintelligence to identify or remediate the vulnerabilities targeted bythe attack. Furthermore, the cost of the acquiring, managing, andmaintaining conventional IDS is overwhelming the end user.

Therefore, a more sophisticated, intelligent technology is provided toresolve these issues. In one embodiment, an intelligent IDS is providedto meet market requirements. The alert data output from a distributionof Snort is integrated with the platform via the SDK, which may add thefollowing functions.

In one embodiment, it cross-references the threat's identifier with thetarget's configuration. The CVE ID, or other identifier, and theDestination IP address are fed into the logic engine where itcross-references the threat with the machine's configuration profile.

In one embodiment, it virtually eliminates false positives and falsenegatives. The backend accurately determines in real time if thetargeted machine is susceptible to the attack. And, if the machine isnot susceptible, it is filtered and reported back as an event and not anincident. No further data or alert is generated, and a managementresponse is not required.

In one embodiment, it remotely remediates the vulnerability. When amachine is identified as vulnerable to an attack, an incident, aremediation function may be provided to the administrator to remotelydeploy the appropriate update to the machine or device, install it,verifies the files and hashes, and document it with change tracking andaudit trail reports.

Table 3 sets forth a plurality of features.

TABLE 3   Supports Windows and UNIX variants Determines if targetedmachine is vulnerable to an attack in real time Filters out erroneous,benign and false positive alerts Remotely patches targetedvulnerabilities in one click Installs in minutes

To this end, erroneous, benign, and false positive data is filtered out,and incidents may be remotely remediated. Therefore, complex threats aremore effectively and efficiently mitigated. Correspondingly, themanagement and maintenance burden on administrators is reduced, savingtime and effort.

FIG. 7 illustrates an intelligent IDS, in accordance with oneembodiment. As shown in 701, the on-site server periodically initiatescommunication with the NOC servers. In 702, updates are pulled from theNOC servers to the on-site server. In 703 a, a sensor monitors andprocesses network traffic, and sends real time alert data to the on-siteserver where it cross-references the data with the backend. In 703 b,centralized IDS console filters alerts; separating events fromincidents. It also offers administrators remote patching function. In704, agents are deployed to each client, accurately identifying whichOS, apps, and updates are installed. In 705, the logic engineautomatically determines which updates are needed to remediate thetargeted machine. As shown in 706, appropriate updates are remotelydeployed, installed, and validated on each client.

In one embodiment, the intelligent patch management and vulnerabilityremediation application automatically updates computer OS andapplication vulnerabilities before they can be exploited by hackers andviruses.

Networks are probed at an ever-increasing frequency for vulnerabilities,which may be exploited with directed compromise attacks. To protect thenetwork, administrators must diligently update or “patch” server andworkstation vulnerabilities, which is a time-consuming and costlyprocess. Further compounding the burden on administrators, best practiceand government compliance directives now require higher standards ofnetwork security to protect consumer privacy and proprietary data, whichmust be documented with change tracking and audit trail reports.Therefore, fully automated technology is provided to resolve theseissues.

In one embodiment, a intelligent application called SysUpdate—the firsttechnology to fully automate the updating and reporting processes, asdescribed below.

In terms of function, one possible embodiment automatically researchesupdates. In collaboration with software development companies, itreceives updates and their respective compatibility and installationguidelines, which are thoroughly reviewed and tested in a lab for systemcompatibility and stability. One embodiment automatically and securelydownloads, and archives, all updates. Once the updates and guidelinesare thoroughly reviewed and tested, they are automatically downloaded toeach customer's on-site server, verified with MD5 hashes, and archivedin a self-populating patch repository database.

One possible embodiment automatically determines the update anddependency requirements for all computers on a network, based on theirindividual operating systems, applications, and previously installedupdates. The logic engine automatically matches the tested updates andtheir guidelines across each computer's configuration profile.

One possible embodiment remotely, securely, and automatically deploysupdates to each computer and device. Updates may be tested on a testgroup, and then queued for release to each computer on the network,consistently in accordance with the policy determined by the networkadministrator.

One possible embodiment automatically verifies the updates are installedand running correctly. Each computer's client agent installs theupdates, and verifies the files and hashes.

One possible embodiment automatically generates change tracking andaudit trail reports. Change tracking and audit trail reports may beselected and printed from the management console reporting modules.Additionally, application license audit reports may be generated, whichlists software installed on each machine, by license key.

Table 4 illustrates possible features in one embodiment.

TABLE 4   Supports Windows, UNIX variants, and network devices Supportsnon-Microsoft applications Logic engine provides system intelligenceFiles verified with SHA1 or MD5 hashes MMC snap-in console with CrystalReports AES encryption

FIG. 8 illustrates an update system, in accordance with one embodiment.As shown in 801, the on-site server periodically initiates communicationwith the off-site NOC servers. In 802, updates are pulled from the NOCservers to the on-site server. In 803, the centralized MMC snap-inconsole offers flexible security policy options and comprehensivereporting capabilities. In 804. agents accurately identifies OS, apps,and updates installed on each client by file versions and hashes. In805, logic engine automatically determines which updates are needed oneach client, taking into account OS, app, and update dependencies. In806, appropriate updates are automatically deployed, installed, andvalidated on each client.

In one embodiment, a secure computer log management application isprovided with fully automated archiving, querying, and reportingoptions.

Best practice directives and government compliancy regulations nowrequire administrators to archive log events over an extended period oftime, and extensively document log and audit trail reports. Withexisting tools, these are time-consuming processes. Furthermore,existing tools transfer logs in clear text and are subject to maliciousmanipulation, and logs may be lost since few utilize guaranteed deliveryprotocols. Therefore, the integrity and security of the log data is notassured. In the event of an internal or external compromise, logs may bedeleted, manipulated, or the network flooded with decoy log data.

The present possible embodiment automatically and continuously transferslogs from each computer into a self-configuring, self-populating,maintenance-free database where they may be archived for years on end.The transfer process utilizes AES encryption for authentication betweenthe client and server, and a guarantee delivery protocol—ensuring nodata is compromised or lost. Flexible cross-correlation queries may berun from a single, remote viewer console, and the data is thenautomatically formatted into reports.

In one embodiment, cross-correlation query type descriptions areprovided. Such embodiment may provide the following three flexiblecross-correlation queries in Table 5, which provide increasing detailand breadth of filtering/sorting capabilities, respectively.

TABLE 5 General Queries—This is the default query. It filters or sortsthe logs of any one computer, by any one of the three log types.Specific Queries —Detailed queries across all machines, and all logtypes. Advanced Queries —Query across any combination of machines, byany combination of sources, events, and log types, over any period oftime.

In one embodiment, features shown in Table 6 may be provided.

TABLE 6 Continuously pulls all logs into a central database, which maybe archived for years on end AES encryption and a guarantee deliveryprotocol ensure logs are not compromised or lost Queries may be acrossany computer, for any log type, over any time frame Automaticallygenerates event log reports—ideal for documenting audit and compliancerequirements Easy download installation

In one embodiment, automated reports may be provided. Query data isautomatically formatted into professional reports Also, a separatereporting interface is available to generate general, machine, and userstatistics. The present embodiment quickly and easily fulfills bestpractice and government compliance requirements for log event archivingand reporting.

FIG. 9 shows a configured network, in accordance with one embodiment.

As shown in 901, the server component automatically configures theapplication, and the database and communicates with the client agents.In 902, client agents are deployed, which then identifies, manages, andcontinuously transfers all logs to the server. In 903, all client logdata may be automatically archived the self-populating database, foryears on end. In 904, from the centralized viewer, general, specific, oradvanced cross-correlation queries may be run. See Table 7. Query andstatistics data is automatically formatted into professional reports toeasily document audit and compliance requirements.

TABLE 7 Filter/Sort By: General Specific Advanced # of Computers Any OneAny One Any # of Log Types Any One All Any Period of Time Last or AllLast or All Any # of Event Detail By ID Only Any One Any Fields * *Defined as Time/Date Written, UserID, ComputerID, EventID, Source, Type,and Category

One possible embodiment provides best practice security policy templatesto proactively and remotely manage and enforce enterprise securitycompliance policies.

Best practice and government compliance directives require higherstandards of network security to protect consumer privacy andproprietary data, which must be consistently enforced, and documentedwith change tracking and audit trail reports for complianceverification. Therefore, a fully automated technology is provided toresolve these issues.

One embodiment offers an intelligent application to manage and enforcesecurity policies—the first technology to fully automate the policyconfiguration, enforcement, and reporting processes, as described below.

In one embodiment, centralized, remote management is provided. Thepolicy compliance and enforcement module is managed via the centralizedmanagement console—in MMC format, and automates the deployment,assessment, and enforcement of the policy chosen.

One embodiment provides standardized policies selected from manystandardized policy templates recommended by NSA, SANS, US Navy, and ISO17799, or custom policy options to formulate policies that meet theindividual needs of any organization.

One possible embodiment automatically determines out-of-complianceparameters for all computers and devices on a network. Based on eachclient's individual policy parameter settings and configuration profile,the system's logic engine automatically reports back each client'sout-of-compliance parameters.

In one embodiment, it remotely, securely, and automatically enforcespolicy to each computer or device. Policy changes may be automaticallyenforced to each computer or device individually, or by group,consistently in accordance with the policy selected by the networkadministrator. Policy configuration profiles are transmitted betweenclient agent and server in an AES encrypted format for security andprivacy. Policy options may be rolled back with one-click.

Automatically generates change tracking and audit trail reports. Changetracking and audit trail reports may be selected and printed from theManagement Console's Reporting Center. Table 8 sets forth some possiblefeatures.

TABLE 8 Supports Windows, UNIX variants, and network devices SupportsNSA, SANS, Navy, ISO 17799 and other standardized policies Logic engineprovides system intelligence One-click policy rollback Automaticallygenerates change tracking and audit trail reports

FIG. 10 shows policy compliance and enforcement, in accordance with oneembodiment.

As shown in 1001, the on-site server periodically initiatescommunication with the off-site NOC servers. In 1002, templates, rules,and updates are pulled from the NOC servers to the on-site server. In1003, a centralized management console offers flexible security policytemplates, options, and comprehensive reporting capabilities. In 1004,agents are automatically deployed to each client, accurately identifyingwhich policy parameters, OS, apps, and updates are applied or installed.In 1005, a logic engine automatically determines which clients are outof compliance. In 1006, appropriate policy changes are automaticallyenforced on each client.

In one embodiment an intelligent IPS may be provided that providesintelligence, accuracy, real-time prevention, and remote patchingfunctions. In one embodiment, it accurately identifies and preventsmalicious code from reaching their destination at the in-line IPSSensor. Thereafter, a security officer may remotely patch the targetedvulnerability.

Conventional IDS/IPS produce an ever-increasing quantity of alert data,including erroneous and false positive data. They also lack theintelligence to identify or remediate the vulnerabilities targeted bythe attack. Furthermore, the cost of the acquiring, managing, andmaintaining conventional IPS is overwhelming the end user.

Therefore, a more sophisticated, intelligent technology is provided toresolve these issues, by offering an intelligent IPS to meet marketrequirements. The alert data output from a standard distribution ofSnort is integrated with the platform via the SDK which accuratelyidentifies attacks, and the attack is terminated at the in-linesensor—as described in the following functions.

One embodiment cross-references the threat's identifier with thetarget's configuration. The in-line Sensor monitors and processestraffic and sends alert data to the on-site server where its logicengine queries the backend in real-time to determine if the destinationIP is vulnerable to the attack.

One possible embodiment provides enhanced flex response. If thedestination IP is vulnerable to the attack, the in-line Sensor iscommanded to immediately drop the exploit packets—preventing the attack.Further, it remotely remediates the vulnerability. When a machine isidentified as vulnerable to an attack, an incident, a remediationfunction is also provided to the administrator to remotely deploy theappropriate update to the machine or device, install it, verifies thefiles and hashes, and documents it with change tracking and audit trailreports.

In one embodiment, attacks are accurately identified and mitigatedbefore they reach their targets, and targeted vulnerabilities may beremotely remediated. Therefore, complex threats are more effectively andefficiently mitigated. Correspondingly, the management and maintenanceburden on administrators is reduced, saving time and effort.

Table 9 illustrates some possible features.

TABLE 9 Supports Windows and UNIX variants Determines in real-time iftargeted machine is vulnerable to an attack, virtually eliminating falsepositives in-line Sensor flex response terminates the attack Remotelypatches targeted vulnerabilities in one click Installs in minutes

FIG. 11 illustrates an intelligent IPS, in accordance with oneembodiment.

As shown in 1101, the on-site server periodically initiatescommunication with the NOC servers. In 1102, updates are pulled from theNOC servers to the on-site server.

In 1103 a, an IPS in-line sensor monitors and processes network traffic,and sends real time alert data to the on-site server where itcross-references the data with the backend. In 1103 b, if thedestination IP is vulnerable to the attack, the in-line Sensor iscommanded in real-time to drop the malicious packets. As shown in 1104,agents are deployed to each client, accurately identifying which OS,apps, and updates are installed. In 1105, the logic engine automaticallydetermines which updates are needed to remediate the targeted machine,and may be remotely deployed from the IPS console. In 1106, appropriateupdates are remotely deployed, installed, and validated on each client.

In one embodiment, an anti-vulnerability SDK is provided. The SDK wasdesigned to be a simple integration pathway to the Anti-Vulnerabilityplatform backend. The SDK is documented and deliverable. The SDK iscompatible with many different programming languages such as C, C++, VB,Java, and others.

The technology is sophisticated, yet all of the details of managing thecommunications are implemented in the library, requiring the developerto only learn a simple function calls as detailed hereinafter. A productarchitect chooses the functionality desired, inserts the providedfunctionality SDK code into the product code. The SDK code may thenquery—via the logic engine—the data warehouse, and in turn may return ananswer to the point product. The architect can then show the results inany format desired in the product's interface. Full vulnerabilityremediation and policy compliance and enforcement functionalities may beintegrated as well.

FIG. 12 illustrates an SDK function call flow, in accordance with oneembodiment.

Hence, the SDK serves as the architect's tool belt or building blocksneeded to quickly and transparently access the Anti-Vulnerabilitybackend and seamlessly integrate the desired functionality into theproduct without changing or complicating the end user experience.

Furthermore, the SDK enables system architects to use theAnti-Vulnerability platform to integrate multiple security products andfunctionalities. Products may then share the same vulnerability dataset, improve system automation and accuracy—increasing efficiencies andminimizing false positives and false negatives, and coordinate policycompliance and enforcement functionalities.

Anti-Vulnerability functions that are accessible via the SDK. Thefunctions are presented in groups, as follows in Table 10.

TABLE 10 Session Management Group Management Functions Client ManagementFunctions Patch Management Functions Polling Functions User ManagementFunctions Miscellaneous Functions Policy Compliance Functions SessionManagement Functions

Table 11 sets forth Session Management Functions

TABLE 11 OpenSession-Parameters: HOST name or IP address, LOGIN andPASSWORD for host Returns: new SESSION Description: This function opensa new session to the OnSite Server CloseSession-Parameters: SESSION toclose Returns: None Description: Closes a session that is no longerneeded IsSessionGood-Parameters: SESSION to test Returns: TRUE or FALSEDescription: returns TRUE if the session is still valid FALSE if it isnot SUGetLastError-Parameters: None Returns: Error code of last error inthe thread Description: Returns the error code of the last SDK error tooccur in this thread SUSetLastError-Parameters: ERROR code to setReturns: None Description: Sets the error code for the thread to bereturned by SUGetLastError GetSDKVersion-Parameters: None Returns: aWORD containing the version of the SDK Description: the MSB of thereturned value is the major version number, the LSB is the minor versionnumber Ping-Parameters: SESSION to use, VALUE to ping with Returns:VALUE on success 0 on failure Description: attempts to pass VALUE to theOnSite Server, which should pass it back.

Table 12 sets forth Group Management Functions.

TABLE 12 CreateGroup-Parameters: Group NAME and Description Returns:GROUP that was just created or 0 on failure Description: This functioncreates a new group with the provided name and DescriptionGetGroups-Parameters: None Returns: A LIST of GROUPs. Description: Thisfunction Returns a list of all configured groups.GetGroupsEx-Parameters: None Returns: A LIST of GROUPINFO structuresDescription: This function Returns a list of all configured groups'information DeleteGroup-Parameters: GROUP to be deleted. Returns:Success or failure Description: This function permanently removes agroup. EditGroup-Parameters: GROUP to be edited, GROUPINFO to be appliedReturns: Success or failure Description: This function changes a GROUP's information GetGroupPolicyOSCategories-Parameters: GROUP to getinformation about Returns: A LIST of OPERATINGSYSYTEMCATEGORYs that havegroup policies configured Description: This function retrieves a list ofoperating system categories that have group policies configuredGetGroupPolicyOSSubCategories-Parameters: GROUP to get informationabout, OPERATINGSYSTEMCATEGORY to get sub category information aboutReturns: A LIST of OPERATINGSYSTEMSUBCATEGORYs Description: Thisfunction retrieves a list of operating system sub-categories ofOPERATINGSYSTEMCATEGORY that have policies for the GROUPGetGroupPolicyInfo-Parameters: GROUPPOLICY to get information about,GROUPPOLICYINFO pointer to receive the information Returns: Success orFailure Description: This function fills the passed GROUPPOLICYINFOstructure with the information for the GROUPPOLICYGetGroupPolicyInfoByOSCat-Parameters: GROUP to get information about,OPERATINGSYSTEMCATEGORY to get the policy for, GROUPPOLICYINFO pointerto receive the information Returns: Success or failure Description: Thisfunction retrieves the information for a policy for theOPERATINGSYSTEMCATEGORY in the GROUPGetGroupPolicyInfoByOSSubCat-Parameters: GROUP to get information about,OPERATINGSYSTEMSUBCATEGORY to get the policy for, GROUPPOLICYINFOpointer to receive the information Returns: Success or failureDescription: This function retrieves the information for a policy forthe OPERATINGSYSTEMSUBCATEGORY in the GROUPDeleteGroupPolicy-Parameters: GROUPPOLICY to delete Returns: Success orfailure Description: This function permanently deletes the GROUPPOLICYEditGroupPolicy-Parameters: GROUPPOLICYINFO with new informationReturns: Success or failure Description: This function updates the grouppolicy (contained in GROUPPOLICYINFO) with the information inGROUPPOLICYINFO AddGroupPolicy-Parameters: GROUP to add the policy to,GROUPPOLICYINFO containg the policy information Returns: Success orFailure Description: This function creates a new group policy andapplies it to the GROUP GetClientsInGroup-Parameters: GROUP to retrievethe clients from Returns: LIST of CLIENTs belonging to the groupDescription: This function retrieves a list of clients that are membersof a specific group GetClientsInGroupEx-Parameters: GROUP to retrievethe clients from Returns: LIST of CLIENTINFOs for clients belonging tothe group Description: This function Returns a list of CLIENTINFOstructures containing information for the clients that belong to thisgroup AddClientToGroup-Parameters: CLIENT to add to a group, GROUP toadd the client to. Returns: Success or failure Description: Thisfunction adds a client to a group RemoveClientFromGroup-Parameters:CLIENT to remove from group, GROUP to remove the client from Returns:Success or failure. Description: This function removes a client from agroup. MoveClientToGroup-Parameters: CLIENT to move, GROUP to moveclient to Returns: Success or Failure Description: This function movesCLIENT to GROUP GetUngroupedClients-Parameters: None Returns: LIST ofungrouped clients Description: This function Returns a LIST of theclients that do not belong to any groupGetUngroupedClientsEx-Parameters: None Returns: LIST of CLIENTINFOstructures Description: This function Returns a LIST of CLIENTINFOstructures for the clients that do not belong to any groupGetGroupInfo-Parameters: GROUP to get information about, GROUPINFOpointer to receive the information Returns: Success or failureDescription: This function retrieves the information for the GROUP

Table 13 sets forth Client Management Functions.

TABLE 13 GetClientInstalledSoftware-Parameters: CLIENT to getinformation about Returns: LIST of SOFTWARE installed on the clientDescription: This function retrieves a list of the software that hasbeen detected on the client GetClientInstalledSoftwareEx-Parameters:CLIENT to get information about Returns: LIST of SOFTWAREINFO forsoftware installed on the client Description: This function returns aLIST of SOFTWAREINFO structures describing the software detected on theclient GetClientInstalledPatches-Parameters: CLIENT to get informationfrom. Returns: LIST of PATCHes corresponding to the installed patches onthe client Description: This function retrieves a list of patches thatwere verified as installed on the last pollingGetClientInstalledPatchesEx-Parameters: CLIENT to get information fromReturns: LIST of PATCHINFO structures corresponding to the installedpatches on the client Description: This function retrieves a LIST ofPATCHINFO structures for patches that were verified as installed on thelast polling GetClientPendingPatches-Parameters: CLIENT to getinformation from. Returns: LIST of PATCHes corresponding to the pendingpatches for the client Description: This function returns a list ofpatches that the client needs (according to group policy) as of the lastpolling. GetClientPendingPatchesEx-Parameters: CLIENT to get informationfrom Returns: A LIST of PATCHINFO structures corresponding to thepending patches for the client Description: This function returns a LISTof PATCHINFO structures for patches that the client needs (according togroup policy) as of the last polling.GetClientPendingServicePack-Parameters: CLIENT to get information fromReturns: SERVICEPACK if a service pack is pending or 0 if notDescription: This function returns a SERVICEPACK if there is a servicepack pending for the client (according to group policy) as of the lastpolling. If there is no service pack pending it returns 0GetClientPendingSoftware-Parameters: CLIENT to get information fromReturns: LIST of SOFTWARE that is pending Description: This functionreturns a list of software that is pending for the client (according togroup policy) as of the last polling GetClientLogs-Parameters: CLIENT toget information from Returns: LIST of LOGs for the client. Description:This function returns a list of logs for a particular client.GetClientLogsEx-Parameters: CLIENT to get information from Returns: LISTof LOGINFO structures Description: This function returns a list ofLOGINFO structures containing log entries for a particular client.DeleteClient-Parameters: CLIENT to delete. Returns: Success or failure.Description: This function removes all information pertaining to thisclient from the SysUpdate database. GetClientOS-Parameters: CLIENT toget information from Returns: OPERATINGSYSTEM installed on clientDescription: This function returns the OPERATINGSYSTEM installed on theclient GetClientServicePack-Parameters: CLIENT to get information fromReturns: SERVICEPACK installed on client or 0 Description: This functionreturns the service pack installed on the client or 0 if the client doesnot have a service pack installed, or if service packs are notapplicable to the client's platform GetClientInfo-Parameters: CLIENT toget information from CLIENTINFO pointer to receive the informationReturns: Success or failure Description: This function fills the passedCLIENTINFO structure with information pertaining to the passed CLIENTGetClientFromIP-Parameters: IP address of client Returns: CLIENT thatcorresponds to the passed IP address Description: This function maps IPaddresses to clients

Table 14 sets forth Patch Management Functions.

TABLE 14 GetPatchInfo-Parameters: PATCH to get information about,PATCHINFO pointer to receive information Returns: Success or failureDescription: This function fills the passed patch info structure withinformation about the passed patch InstallPatchForClient-Parameters:CLIENT to install the patch on, PATCH to install Returns: Success orfailure Description: This function deploys the patch to the client.Installation proceeds asynchronously InstallPatchForGroup-Parameters:GROUP to install the patch on, PATCH to install Returns: Success orfailure Description: This function deploys the patch to all clients inthe group InstallAllPendingForClient-Parameters: CLIENT to installpatches on Returns: Success or failure Description: This functiondeploys all pending patches for a client to the clientInstallAllPendingForGroup-Parameters: GROUP to install patches onReturns: Success or failure Description: This function deploys allpending patches to all clients in a groupRejectPatchForClient-Parameters: CLIENT to reject patch for, PATCH toreject Returns: Success or failure Description: This function rejects apatch for a client. This patch will not be queued down or installedRejectPatchForGroup-Parameters: GROUP to reject patch for, PATCH toreject Returns: Success or failure Description: This function rejects apatch for every client in a group. This patch will not be queued down orinstalled RequeuePatchForClient-Parameters: CLIENT to requeue the patchfor, PATCH to requeue Returns: Success or failure Description: Thisfunction requeues a previously rejected patch for a clientRequeuePatchForGroup-Parameters: GROUP to requeue the patch for, PATCHto requeue Returns: Success or failure Description: This functionrequeues a previously rejected patch for every client in a groupRemovePatchFromClient-Parameters: CLIENT to remove patch from, PATCH toremove Returns: Success or failure Description: This function willuninstall a patch from a client RemovePatchFromGroup-Parameters: GROUPto remove patch from, PATCH to remove Returns: Success or failureDescription: This function will uninstall a patch for every client in agroup InstallServicePackForClient-Parameters: CLIENT to install servicepack on, SERVICEPACK to install on client Returns: Success or failureDescription: This function will install a service pack on a clientInstallServicePackForGroup-Parameters: GROUP to install service pack on,SERVICEPACK to install Returns: Success or failure Description: Thisfunction will install a service pack on every client in a groupInstallSoftwareForClient-Parameters: CLIENT to install software updateon, SOFTWARE to install Returns: Success or failure Description: Thisfunction will install a software update on a client InstallSoftwareForGroup-Parameters: GROUP to install software update on,SOFTWARE to install Returns: Success or failure Description: Thisfunction will install a software update on every client in a group.GetCveIDsFromPatch-Parameters: PATCH to get CveIDs from Returns: A LISTof CVEIDs Description: This function returns a list of CVEIDs thecorrespond to the PATCH

Table 15 sets forth Polling Functions.

TABLE 15 PollClient-Parameters: CLIENT to poll Returns: Success orfailure. Description: This function causes a client to be polled by theOnSite Server immediately. PollGroup-Parameters: GROUP to poll Returns:Success or failure. Description: This function causes all the clients ina particular group to be polled immediately. PollAll-Parameters: NONEReturns: Success or failure. Description: This function causes allclients to be polled immediately.

Table 16 sets forth User Management Functions.

TABLE 16 GetUsers-Parameters: None Returns: A LIST of USERs Description:This function returns a list of all users for the systemGetUserinfo-Parameters: USER to get information about, USERINFO pointerto receive the information Returns: Success or failure Description: Thisfunction populates the passed USERINFO structure with information aboutthe passed USER GetUserGroupPrivileges-Parameters: USER to getinformation about Returns: A LIST of USERGROUPPRIVILEGEs Description:This function returns a LIST of USERGROUPPRIVILEGES representing theprivileges that a particular user hasGetUserGroupPrivilegesEx-Parameters: USER to get information aboutReturns: A LIST of USERGROUPPRIVILEGEINFO structures Description: Thisfunction returns a LIST of USERGROUPPRIVILEGEINFO structuresrepresenting the privileges that a particular user hasGetUserGroupPrivilegeInfo-Parameters: USERGROUPPRIVILEGE to getinformation about, USERGROUPPRIVILEGEINFO pointer to receive informationReturns: Success or failure Description: This function populates thepassed USERGROUPPRIVILEGEINFO structure with the details of theparticular privilege GetUserGroupPrivilegeInfoByGroup-Parameters: USERto get information about, GROUP to get information for,USERGROUPPRIVILEGEINFO pointer to populate Returns: Success or FailureDescription: This function populates the passed USERGROUPPRIVILEGEINFOstructure with the detailed information regarding the permissions thatthe passed user has on the passed groupAddUserGroupPrivilege-Parameters: USERGROUPPRIVILEGEINFO structure toadd Returns: Success or failure Description: This function adds aUSERGROUPPRIVILEGE EditUserGroupPrivilege-Parameters:USERGROUPPRIVILEGEINFO with new values Returns: Success or failureDescription: This function edits the USERGROUPPRIVILEGEINFO structurepassed in, assign it the new values DeleteUserGroupPrivilege-Parameters:USERGROUPPRIVILEGE to delete Returns: Success or failure Description:This function deletes the passed USERGROUPPRIVILEGE from the systemAddUser-Parameters: USERNAME, PASSWORD, and USERTYPE Returns: USERrepresenting the user that was just created Description: This functioncreates a new user with the provided username, password, and type, andreturns a USER representing the new user or 0 in the case of an errorDeleteUser-Parameters: USER to delete Returns: Success or failureDescription: This function permanently deletes the USER from the systemalong with any privileges the user may have hadChangeUserPassword-Parameters: USER to change password for, new PASSWORDReturns: Success or failure Description: This function changes thepassword for a user ChangeUserRole-Parameters: USER to change role, ROLEto change to Returns: Success or failure Description: This Functionchanges a user's role GetUserFromName-Parameters: USERNAME Returns: USERcorresponding to the passed user name Description: This functionprovides a mapping from user names to USERs

Table 17 sets forth Miscellaneous Functions.

TABLE 17 CreateList-Parameters: None Returns: A new, empty, LISTDescription: This functions creates a new LIST that is initially emptyGetListItemEx-Parameters: LIST to retrieve item from, INDEX of item toretrieve, VOID pointer to receive item Returns: Success or failureDescription: This function populates the memory pointed to by VOID withthe contents of the LIST item at INDEX GetListSize-Parameters: LIST toget the size of Returns: the size of the LIST Description: This functionreturns the number of elements currently in the listAddItemToList-pointer to LIST to add the item to, LONG item to addReturns: None Description: This function adds an “item” (such as a GROUPor a CLIENT) to a LIST AddClientInfoExToList-See AddItemToListAddGroupInfoToList-See AddItemToList AddPatchInfoExToList-SeeAddItemToList AddSoftwareInfoToList-See AddItemToListAddSoftwareCategoryInfoToList-See AddItemToListAddUserGroupPrivilegeInfoExToList-See AddItemToListRemoveItemFromList-Parameters: pointer to LIST to remove the item from,INDEX of item to remove Returns: None Description: This function removesthe item at INDEX from the LIST FreeList-LIST to deallocate Returns:None Description: This function deallocates the resources used by LISTGetSoftwareInfo-Parameters: SOFTWARE to get information for,SOFTWAREINFO pointer to hold the information Returns: Success or failureDescription: This function populates the SOFTWAREINFO structure pointedat with information regarding the SOFTWARE GetLogInfo-Parameters: LOG toget information about, LOGINFO pointer to contain the informationReturns: Success or failure Description: This function populates theLOGINFO structure pointed at with information regarding the LOGGetSoftwareCategories-Parameters: None Returns: A LIST ofSOFTWARECATEGORYs Description: This function returns a LIST ofSOFTWARECATEGORYs GetSoftwareCategoriesEx-Parameters: None Returns: ALIST of SOFTWARECATEGORYINFO structures Description: This functionreturns LIST of SOFTWARECATEGORYINFO structures for every softwarecategory known on the systemGetSoftwareCategoriesForOperatingSystemCategory-Parameters: anOPERATINGSYSTEMCATEGORY to get information for Returns: A LIST ofSOFTWARECATEGORYs Description: This function returns a LIST of softwarecategories for the passed operating system category.GetSoftwareCategoriesForOperatingSystemCategoryEx-As above only,returning the appropriate “info” structures in the listGetSoftwareCategoryInfo-Parameters: SOFTWARECATEGORY to get informationfor, SOFTWARECATEGORYIFNO pointer to contain the information Returns:Success or failure

Table 18 sets forth Policy Compliance Functions.

These functions are provided in a separate source tree (policy tree) forthe Policy Compliance and Enforcement module. Function include:Password/system access policies, log configurations, audit settings,user/group privilege rights, general service settings, servicepermissions, registry values, registry permissions, file permissions. Itcan also perform deltas on and get information about: groups, users,services, and all the “Run” registry keys.

The function calls are being integrated into the live production treeand subject to change.

TABLE 18 GetPolicyItemInfo-As GetOperatingSystemInfo for POLICYITEM andPOLICYITEMINFO InstallPolicyItemForClient-As InstallPatchForClient forPOLICYITEM InstallPolicyItemForGroup-As InstallPatchForGroup forPOLICYITEM InstallAllPendingPolicyItemsForClient-AsInstallAllPendingPatchesForClient for POLICYITEMInstallAllPendingPolicyItemsForGroup-As InstallAllPendingPatchesForGroupfor POLICYITEM RemovePolicyItemFromClient-As RemovePatchForClient forPOLICYITEM RemovePolicyItemFromGroup-As RemovePatchFromGroup forPOLICYITEM

All publications, prior applications, and other documents cited hereinare hereby incorporated by reference in their entirety as if each hadbeen individually incorporated by reference and fully set forth.

While the invention has been illustrated and described in detail in thedrawings and foregoing description, the same is to be considered asillustrative and not restrictive in character, it being understood thatonly the preferred embodiments have been shown and described and thatall changes and modifications that would occur to one skilled in therelevant art are desired to be protected.

1. An apparatus, comprising: an intrusion prevention system configuredto: receive a result of at least one operation performed on at least oneof a plurality of networked devices, the at least one operation based onfirst information from at least one first data storage identifying aplurality of potential vulnerabilities including at least one firstpotential vulnerability and at least one second potential vulnerability,the at least one operation configured for: identifying at least oneconfiguration associated with the at least one networked device, anddetermining that the at least one networked device is actuallyvulnerable to at least one actual vulnerability, based on the identifiedat least one configuration and the first information from the at leastone first data storage identifying the plurality of potentialvulnerabilities, such that second information associated with the resultis stored in at least one second data storage separate from the at leastone first data storage, the second information relating to the at leastone actual vulnerability to which the at least one networked device isactually vulnerable; cause display, via at least one user interface, aplurality of techniques including a first technique for utilizing anintrusion prevention system component for occurrence mitigation, and asecond technique for utilizing a firewall for occurrence mitigation;allow receipt of: user input causing selection of the first techniquefor utilizing the intrusion prevention system component for occurrencemitigation; user input causing selection of the second technique forutilizing the firewall for occurrence mitigation; apply, based on theuser input causing selection of the first technique for utilizing theintrusion prevention system component for occurrence mitigation, thefirst technique for utilizing the intrusion prevention system componentfor occurrence mitigation; apply, based on the user input causingselection of the second technique for utilizing the firewall foroccurrence mitigation, the second technique for utilizing the firewallfor occurrence mitigation; identify: for the at least one networkeddevice, a first occurrence including at least one first occurrencepacket, and for the at least one networked device, a second occurrenceincluding at least one second occurrence packet; determine: that thefirst occurrence including the at least one first occurrence packetdirected to the at least one networked device is capable of takingadvantage of the at least one of the actual vulnerability to which theat least one networked device is actually vulnerable; that the secondoccurrence including the at least one second occurrence packet directedto the at least one networked device is not capable of taking advantageof the at least one of the actual vulnerability to which the at leastone networked device is actually vulnerable; and cause a reporting of atleast the first occurrence based on the determination that the firstoccurrence including the at least one first occurrence packet is capableof taking advantage of the at least one of the actual vulnerability towhich the at least one networked device is actually vulnerable.
 2. Theapparatus of claim 1, wherein the intrusion prevention system includesintegrated intrusion prevention functionality for supporting the firsttechnique and firewall functionality for supporting the secondtechnique, such that the intrusion prevention functionality and thefirewall functionality are both supported by a security component of theintrusion prevention system that in turn supports at least one aspect ofthe determination that the first occurrence including the at least onefirst occurrence packet directed to the at least one networked device iscapable of taking advantage of the at least one of the actualvulnerability to which the at least one networked device is actuallyvulnerable, the intrusion prevention system further including logic thatreceives the second information and utilizes the second information toconditionally cause the display of, as a function of an existence of oneor more actual vulnerabilities, one or more of the plurality oftechniques to allow selective utilization of the intrusion preventionfunctionality and the firewall functionality, so that only relevanttechniques are displayed for selection to reduce false positives inconnection with both the intrusion prevention functionality and thefirewall functionality.
 3. The apparatus of claim 1, wherein theintrusion prevention system includes integrated intrusion preventionfunctionality for supporting the first technique and firewallfunctionality for supporting the second technique, such that theintrusion prevention functionality and the firewall functionality areboth supported by a security component of the intrusion preventionsystem that in turn supports at least one aspect of the determinationthat the first occurrence including the at least one first occurrencepacket directed to the at least one networked device is capable oftaking advantage of the at least one of the actual vulnerability towhich the at least one networked device is actually vulnerable, theintrusion prevention system further including logic that receives actualvulnerability information and utilizes the actual vulnerabilityinformation to relevantly cause the display of, as a function of one ormore actual vulnerabilities identified utilizing the actualvulnerability information, multiple of the plurality of techniques toallow selective utilization of the intrusion prevention functionalityand the firewall functionality.
 4. The apparatus of claim 1, wherein theintrusion prevention system is configured such that different userselections are capable of being received for different devices, forallowing different techniques including the first technique and thesecond technique to be selectively applied to the different devices fordifferent actual vulnerabilities, such that the different userselections are capable of resulting in: only the at least one firstmitigation technique being selectively applied to at least one firstdevice, only the at least one second mitigation technique beingselectively applied to at least one second device, and both the at leastone first mitigation technique and the at least one second mitigationtechnique being selectively applied to at least one third device.
 5. Theapparatus of claim 1, wherein the intrusion prevention system isconfigured such that the first technique is automatically appliedutilizing a first communication, and the second technique isautomatically applied utilizing a second communication; wherein theintrusion prevention system includes intrusion prevention functionalityfor supporting the first technique and firewall functionality forsupporting the second technique, the intrusion prevention system furtherconfigured to receive the second information to conditionally causedisplay of, as a function of an existence of the at least one actualvulnerability, the plurality of techniques to allow selectiveutilization of the intrusion prevention functionality and the firewallfunctionality, so that only relevant techniques are caused to bedisplayed to reduce false positives in connection with both theintrusion prevention functionality and the firewall functionality;wherein the apparatus is further configured such that different userselections are capable of being received for different devices, forallowing different techniques including the first technique and thesecond technique to be selectively applied to the different devices fordifferent actual vulnerabilities, such that the different userselections are capable of resulting in: only the at least one firstmitigation technique being selectively applied to at least one firstdevice, only the at least one second mitigation technique beingselectively applied to at least one second device, and both the at leastone first mitigation technique and the at least one second mitigationtechnique being selectively applied to at least one third device.
 6. Anapparatus, comprising: at least one platform; an intrusion preventionsystem configured to communicative couple with the at least oneplatform; a firewall configured to communicative couple with the atleast one platform; at least one first data storage configured tocommunicative couple with the at least one platform; and at least onesecond data storage configured to communicative couple with the at leastone platform; said at least one platform configured to: receive a resultof at least one operation in connection with at least one of a pluralityof networked devices, the at least one operation based on firstinformation from the at least one first data storage identifying aplurality of potential vulnerabilities including at least one firstpotential vulnerability and at least one second potential vulnerability,the at least one operation configured for: identifying at least oneconfiguration associated with the at least one networked device, anddetermining that the at least one networked device is actuallyvulnerable to at least one actual vulnerability, based on the identifiedat least one configuration and the first information from the at leastone first data storage identifying the plurality of potentialvulnerabilities, such that second information associated with the resultis stored in the at least one second data storage separate from the atleast one first data storage, the second information relating to the atleast one actual vulnerability to which the at least one networkeddevice is actually vulnerable; cause display, via at least one userinterface, a plurality of techniques including a first technique forutilizing the intrusion prevention system for occurrence mitigation, asecond technique for utilizing the firewall for occurrence mitigation;allow receipt of: user input causing selection of the first techniquefor utilizing the intrusion prevention system for occurrence mitigation,and user input causing selection of the second technique for utilizingthe firewall for occurrence mitigation; based on the user input causingselection of the first technique for utilizing the intrusion preventionsystem for occurrence mitigation, automatically apply the firsttechnique for utilizing the intrusion prevention system for occurrencemitigation; based on the user input causing selection of the secondtechnique for utilizing the firewall for occurrence mitigation,automatically apply the second technique for utilizing the firewall foroccurrence mitigation; cause identification of: in connection with theat least one networked device, a first occurrence including at least onefirst occurrence packet directed to the at least one networked device,and in connection with the at least one networked device, a secondoccurrence including at least one second occurrence packet directed tothe at least one networked device; determine: that the first occurrenceincluding the at least one first occurrence packet directed to the atleast one networked device is capable of taking advantage of the atleast one of the actual vulnerability to which the at least onenetworked device is actually vulnerable; that the second occurrenceincluding the at least one second occurrence packet directed to the atleast one networked device is not capable of taking advantage of the atleast one of the actual vulnerability to which the at least onenetworked device is actually vulnerable; and cause a reporting of atleast the first occurrence based on the determination that the firstoccurrence including the at least one first occurrence packet directedto the at least one networked device is capable of taking advantage ofthe at least one of the actual vulnerability to which the at least onenetworked device is actually vulnerable.
 7. The apparatus of claim 6,wherein the intrusion prevention system includes integrated intrusionprevention functionality for supporting the first technique and firewallfunctionality for supporting the second technique, such that theintrusion prevention functionality and the firewall functionality areboth supported by a security component of the intrusion preventionsystem that in turn supports at least one aspect of the determinationthat the first occurrence including the at least one first occurrencepacket directed to the at least one networked device is capable oftaking advantage of the at least one of the actual vulnerability towhich the at least one networked device is actually vulnerable, theintrusion prevention system further including logic that receives thesecond information and utilizes the second information to conditionallycause the display of, as a function of an existence of one or moreactual vulnerabilities, one or more of the plurality of techniques toallow selective utilization of the intrusion prevention functionalityand the firewall functionality, so that only relevant techniques aredisplayed for selection to reduce false positives in connection withboth the intrusion prevention functionality and the firewallfunctionality.
 8. The apparatus of claim 6, wherein the intrusionprevention system includes integrated intrusion prevention functionalityfor supporting the first technique and firewall functionality forsupporting the second technique, such that the intrusion preventionfunctionality and the firewall functionality are both supported by asecurity component of the intrusion prevention system that in turnsupports at least one aspect of the determination that the firstoccurrence including the at least one first occurrence packet directedto the at least one networked device is capable of taking advantage ofthe at least one of the actual vulnerability to which the at least onenetworked device is actually vulnerable, the intrusion prevention systemfurther including logic that receives actual vulnerability informationand utilizes the actual vulnerability information to relevantly causethe display of, as a function of one or more actual vulnerabilitiesidentified utilizing the actual vulnerability information, multiple ofthe plurality of techniques to allow selective utilization of theintrusion prevention functionality and the firewall functionality. 9.The apparatus of claim 6, wherein the intrusion prevention system isconfigured such that different user selections are capable of beingreceived for different devices, for allowing different techniquesincluding the first technique and the second technique to be selectivelyapplied to the different devices for different actual vulnerabilities,such that the different user selections are capable of resulting in:only the at least one first mitigation technique being selectivelyapplied to at least one first device, only the at least one secondmitigation technique being selectively applied to at least one seconddevice, and both the at least one first mitigation technique and the atleast one second mitigation technique being selectively applied to atleast one third device.
 10. The apparatus of claim 6, wherein theintrusion prevention system is configured such that the first techniqueis automatically applied utilizing a first communication, and the secondtechnique is automatically applied utilizing a second communication;wherein the intrusion prevention system includes intrusion preventionfunctionality for supporting the first technique and firewallfunctionality for supporting the second technique, the intrusionprevention system further configured to receive the second informationto conditionally cause display of, as a function of an existence of theat least one actual vulnerability, the plurality of techniques to allowselective utilization of the intrusion prevention functionality and thefirewall functionality, so that only relevant techniques are caused tobe displayed to reduce false positives in connection with both theintrusion prevention functionality and the firewall functionality;wherein the apparatus is further configured such that different userselections are capable of being received for different devices, forallowing different techniques including the first technique and thesecond technique to be selectively applied to the different devices fordifferent actual vulnerabilities, such that the different userselections are capable of resulting in: only the at least one firstmitigation technique being selectively applied to at least one firstdevice, only the at least one second mitigation technique beingselectively applied to at least one second device, and both the at leastone first mitigation technique and the at least one second mitigationtechnique being selectively applied to at least one third device. 11.The apparatus of claim 6, wherein the intrusion prevention system isconfigured such that which of the networked devices have weaknesses isdetermined by directly querying a firmware or operating system thereof.12. The apparatus of claim 6, wherein the intrusion prevention system isconfigured such that at least one of: said result includes the secondinformation; said at least one first data storage includes at least onefirst database; said at least one first data storage is a component of anetwork operations center (NOC) server; said at least one second datastorage includes at least one second database; said first information isfrom the at least one first data storage via at least one of: receivingat least one update therefrom; pulling at least one update therefrom,communicating therewith, or synchronizing therewith; said at least oneoperation includes a vulnerability scan operation; said at least oneoperation is automatic; said identifying the at least one configurationis automatic; said at least one actual vulnerability includes at leastone of the potential vulnerabilities to which the at least one networkeddevice is determined to be actually vulnerable based on identified atleast one configuration; said at least one configuration includes atleast one of: service pack information, one or more elements containedin files including at least one of an *.ini or *.conf file, registryinformation, identification of an operating system, identification of asoftware version, or identification of software; said determining thatthe at least one networked device is actually vulnerable to the at leastone actual vulnerability includes at least one of: matching theidentified at least one configuration with a guideline associated withat least one update, or cross-referencing an identifier with theconfiguration; said second information identifies the at least oneactual vulnerability to which the at least one networked device isactually vulnerable; said second information is stored in the at leastone second storage when it is utilized; said indication of the at leastone actual vulnerability to which the at least one networked device isactually vulnerable includes an identification of the at least oneactual vulnerability to which the at least one networked device isactually vulnerable; said computer program product is embodied on asingle non-transitory computer readable medium; said first technique andsecond technique are of different types; at least one of said first orsecond techniques include at least one of remediation techniques,mitigation techniques, attack mitigation techniques, or vulnerabilitymitigation techniques; said occurrence mitigation includes at least oneof removing the at least one actual vulnerability, occurrenceprevention, or reducing an effect of a particular occurrence; said firsttechnique for utilizing the intrusion prevention system for occurrencemitigation and the second technique for utilizing the firewall foroccurrence mitigation are displayed via the same user interface; saidfirst technique for utilizing the intrusion prevention system foroccurrence mitigation and the second technique for utilizing thefirewall for occurrence mitigation are displayed via different userinterface elements; said first technique for utilizing the intrusionprevention system for occurrence mitigation, and the second techniquefor utilizing the firewall for occurrence mitigation, are displayed viathe at least one user interface utilizing at least one of options orgraphical user interface elements; said first technique for utilizingthe intrusion prevention system for occurrence mitigation results in thefirst technique being automatically applied at a later time; at leastone of said first or second techniques, after the user selectionthereof, is automatically applied at a later time; said user inputcausing selection of the first technique for utilizing the intrusionprevention system for occurrence mitigation results in the firsttechnique being automatically applied at a later time; said user inputcausing selection of the first technique and the user input causingselection of the second technique including separate user inputs; saidautomatic application of the first technique puts a policy in place forbeing utilized at a later time; said automatic application of the secondtechnique puts a policy in place for being utilized at a later time; atleast one of said first or second techniques, after the automaticapplication thereof, is utilized at a later time for the occurrencemitigation; said user input selecting the first technique is receivedutilizing the at least one user interface; said user input causingselection of the first technique for utilizing the intrusion preventionsystem for occurrence mitigation specifically identifies the firsttechnique; said user input causing selection of the second technique forutilizing the firewall for occurrence mitigation specifically identifiesthe second technique; said user input causing selection of the firsttechnique for utilizing the intrusion prevention system for occurrencemitigation is received in response to the display of the firsttechnique; said user input causing selection of the second technique forutilizing the firewall for occurrence mitigation is received inconnection with the display of the second technique; said firsttechnique for utilizing the intrusion prevention system for occurrencemitigation involves an intrusion prevention system action that preventsan attack; said second technique for utilizing the firewall foroccurrence mitigation includes a firewall action that blocks an attack;said first technique for utilizing the intrusion prevention system foroccurrence mitigation utilizes the intrusion prevention system to deploya patch utilizing an update component; said second technique forutilizing the firewall for occurrence mitigation utilizes the firewallto deploy a patch utilizing an update component; said automaticapplication of the first technique for utilizing the intrusionprevention system for occurrence mitigation includes the determinationthat the first occurrence including the at least one first occurrencepacket directed to the at least one networked device is capable oftaking advantage of the at least one of the actual vulnerability towhich the at least one networked device is actually vulnerable; saidautomatic application of the first technique for utilizing the intrusionprevention system for occurrence mitigation results in the determinationthat the first occurrence including the at least one first occurrencepacket directed to the at least one networked device is capable oftaking advantage of the at least one of the actual vulnerability towhich the at least one networked device is actually vulnerable; saidautomatic application of the first technique for utilizing the intrusionprevention system for occurrence mitigation results from thedetermination that the first occurrence including the at least one firstoccurrence packet directed to the at least one networked device iscapable of taking advantage of the at least one of the actualvulnerability to which the at least one networked device is actuallyvulnerable; said intrusion prevention system and the firewall areseparate; said intrusion prevention system and the firewall areintegrated on the same single platform; said first occurrence includesan attack; said first occurrence includes an incident and said secondoccurrence includes an event; said determination that the firstoccurrence including the at least one first occurrence packet directedto the at least one networked device is capable of taking advantage ofthe at least one of the actual vulnerability to which the at least onenetworked device is actually vulnerable, is carried out utilizing atleast one of vulnerability identifiers, profiles, threat information, orthe second information; said reporting includes reporting of the secondoccurrence; said reporting is carried out utilizing a log; or said atleast one first occurrence packet of the first occurrence is preventedby terminating or dropping the same
 13. An intrusion prevention system,comprising: means for receiving a result of at least one operationperformed on at least one of a plurality of networked devices, the atleast one operation based on first information from at least one firstdata storage identifying a plurality of potential vulnerabilitiesincluding at least one first potential vulnerability and at least onesecond potential vulnerability, the at least one operation configuredfor: identifying at least one configuration associated with the at leastone networked device, and determining that the at least one networkeddevice is actually vulnerable to at least one actual vulnerability,based on the identified at least one configuration and the firstinformation from the at least one first data storage identifying theplurality of potential vulnerabilities, such that second informationassociated with the result is stored in at least one second data storageseparate from the at least one first data storage, the secondinformation relating to the at least one actual vulnerability to whichthe at least one networked device is actually vulnerable; means forcausing display of, via at least one user interface, a plurality oftechniques including a first technique for utilizing an intrusionprevention system for occurrence mitigation, and a second technique forutilizing a firewall for occurrence mitigation; means for receiving userinput causing selection of the first technique for utilizing theintrusion prevention system for occurrence mitigation and user inputcausing selection of the second technique for utilizing the firewall foroccurrence mitigation; means for: based on the user input causingselection of the first technique for utilizing the intrusion preventionsystem for occurrence mitigation, applying the first technique forutilizing the intrusion prevention system for occurrence mitigation; andbased on the user input causing selection of the second technique forutilizing the firewall for occurrence mitigation, applying the secondtechnique for utilizing the firewall for occurrence mitigation; meansfor identifying: for the at least one networked device, a firstoccurrence including at least one first occurrence packet, and for theat least one networked device, a second occurrence including at leastone second occurrence packet; code for determining: that the firstoccurrence including the at least one first occurrence packet directedto the at least one networked device is capable of taking advantage ofthe at least one of the actual vulnerability to which the at least onenetworked device is actually vulnerable, and that the second occurrenceincluding the at least one second occurrence packet directed to the atleast one networked device is not capable of taking advantage of the atleast one of the actual vulnerability to which the at least onenetworked device is actually vulnerable; and means for causing areporting of at least the first occurrence based on the determinationthat the first occurrence including the at least one first occurrencepacket is capable of taking advantage of the at least one of the actualvulnerability to which the at least one networked device is actuallyvulnerable.
 14. The intrusion prevention system of claim 13, wherein theintrusion prevention system includes integrated intrusion preventionfunctionality for supporting the first technique and firewallfunctionality for supporting the second technique, such that theintrusion prevention functionality and the firewall functionality areboth supported by a security component of the system that in turnsupports at least one aspect of the determination that the firstoccurrence including the at least one first occurrence packet directedto the at least one networked device is capable of taking advantage ofthe at least one of the actual vulnerability to which the at least onenetworked device is actually vulnerable, the intrusion prevention systemfurther including logic that receives the second information andutilizes the second information to conditionally display, as a functionof an existence of one or more actual vulnerabilities, one or more ofthe plurality of techniques to allow selective utilization of theintrusion prevention functionality and the firewall functionality, sothat only relevant techniques are displayed for selection to reducefalse positives in connection with both the intrusion preventionfunctionality and the firewall functionality.
 15. The intrusionprevention system of claim 13, wherein the intrusion prevention systemincludes integrated intrusion prevention functionality for supportingthe first technique and firewall functionality for supporting the secondtechnique, the intrusion prevention system further including means forreceiving the second information and utilizing the second information toconditionally display, as a function of an existence of one or moreactual vulnerabilities, one or more of the plurality of techniques toallow selective utilization of the intrusion prevention functionalityand the firewall functionality, so that only relevant techniques aredisplayed for selection to reduce false positives in connection withboth the intrusion prevention functionality and the firewallfunctionality.
 16. The intrusion prevention system of claim 13, whereinthe intrusion prevention system includes integrated intrusion preventionfunctionality for supporting the first technique and firewallfunctionality for supporting the second technique, such that theintrusion prevention functionality and the firewall functionality areboth supported by a security component of the system that in turnsupports at least one aspect of the determination that the firstoccurrence including the at least one first occurrence packet directedto the at least one networked device is capable of taking advantage ofthe at least one of the actual vulnerability to which the at least onenetworked device is actually vulnerable, the system further includinglogic that receives actual vulnerability information and utilizes theactual vulnerability information to relevantly display, as a function ofone or more actual vulnerabilities identified utilizing the actualvulnerability information, multiple of the plurality of techniques toallow selective utilization of the intrusion prevention functionalityand the firewall functionality.
 17. The intrusion prevention system ofclaim 13, wherein the intrusion prevention system is configured suchthat different user selections are capable of being received fordifferent devices, for allowing different techniques including the firsttechnique and the second technique to be selectively applied to thedifferent devices for different actual vulnerabilities, such that thedifferent user selections are capable of resulting in: only the at leastone first mitigation technique being selectively applied to at least onefirst device, only the at least one second mitigation technique beingselectively applied to at least one second device, and both the at leastone first mitigation technique and the at least one second mitigationtechnique being selectively applied to at least one third device. 18.The intrusion prevention system of claim 13, wherein the intrusionprevention system includes integrated intrusion prevention functionalityfor supporting the first technique and firewall functionality forsupporting the second technique, the intrusion prevention system furtherincluding means for receiving the second information and utilizing thesecond information to conditionally display, as a function of anexistence of one or more actual vulnerabilities, one or more of theplurality of techniques to allow selective utilization of the intrusionprevention functionality and the firewall functionality, so that onlyrelevant techniques are displayed for selection to reduce falsepositives in connection with both the intrusion prevention functionalityand the firewall functionality; wherein the intrusion prevention systemis further configured such that different user selections are capable ofbeing received for different devices, for allowing different techniquesincluding the first technique and the second technique to be selectivelyapplied to the different devices for different actual vulnerabilities,such that the different user selections are capable of resulting in:only the at least one first mitigation technique being selectivelyapplied to at least one first device, only the at least one secondmitigation technique being selectively applied to at least one seconddevice, and both the at least one first mitigation technique and the atleast one second mitigation technique being selectively applied to atleast one third device.